Use a new grouping strategy for dependabot updates #389
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
part:tooling
There was a problem hiding this comment.
Pull Request Overview
This PR updates the dependabot grouping strategy by separating patch and minor update groups and adding dedicated groups for repo-config and mkdocstrings dependencies.
- Separates patch and minor update groups with tailored update-type filters and exclusions
- Introduces new groups for repo-config and mkdocstrings dependencies
- Updates inline documentation to reflect the new grouping logic
.github/dependabot.yml
Outdated
| # managed, but they'll create one PR per dependency, as breaking is | ||
| # expected so it might need manual intervention. | ||
| # Finally we group some dependencies that are related to each other, and | ||
| # usually needs to be updated together. |
There was a problem hiding this comment.
[nitpick] Consider changing 'needs' to 'need' to agree with the plural subject 'dependencies'.
Suggested change
| # usually needs to be updated together. | |
| # usually need to be updated together. |
|
Will force-merge too, apparently it worked but it took it some time to get the new PRs out, but we need to group repo-config updates. I was also thinking that probably another strategy makes more sense, based on likelihood of breaking changes. |
We group patch updates as they should always work. We also group minor updates, as it works too for most libraries, typically except libraries that don't have a stable release yet (v0.x.x branch), so we make some exceptions for them. Major updates and dependencies excluded by the above groups are still managed, but they'll create one PR per dependency, as breaking is expected so it might need manual intervention. Finally we group some dependencies that are related to each other, and usually need to be updated together. Signed-off-by: Leandro Lucarella <[email protected]>
llucax
force-pushed
the
repo-config-dependabot
branch
from
e82f054 to
b0ac3d1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We group patch updates as they should always work.
We also group minor updates, as it works too for most libraries, typically except libraries that don't have a stable release yet (v0.x.x branch), so we make some exceptions for them.
Major updates and dependencies excluded by the above groups are still managed, but they'll create one PR per dependency, as breaking is expected so it might need manual intervention.
Finally we group some dependencies that are related to each other, and usually needs to be updated together.